-
Notifications
You must be signed in to change notification settings - Fork 197
[8.19] (backport #10343) feat: utilise continue_on_err in beatsauthextension #10443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 8.19
Are you sure you want to change the base?
Conversation
Cherry-pick of 0c0dada has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
This pull request has not been merged yet. Could you please review and merge it @pkoutsovasilis? 🙏 |
* feat: rework elasticsearch output translation to otel config to exclude validation errors * ci: add integration test (cherry picked from commit 0c0dada) # Conflicts: # internal/pkg/otel/translate/otelconfig.go
a307675
to
78ba0f1
Compare
@pkoutsovasilis is this backport waiting on some other dependencies to merge into |
What does this PR do?
This PR improves error handling for Elasticsearch output configurations in the Hybrid Elastic Agent by:
Moving partially configuration translation ownership: Relocates some of the Elasticsearch output translation logic from the beats library (
libbeat/otelbeat/oteltranslate/outputs/elasticsearch
) into the elastic-agent package (internal/pkg/otel/translate/output_elasticsearch.go
). In the future we should do a full transition to elastic-agent repo as this gives elastic-agent full control over the translation.Enabling graceful error handling: Adds
continue_on_error: true
to the beatsauth extension configuration ingetBeatsAuthExtensionConfig()
. This prevents the OpenTelemetry collector from exiting on startup when encountering invalid SSL configurations (e.g., missing certificate files) respective PR.Why is it important?
When an Elasticsearch output has invalid configuration (like a missing SSL certificate), the collector exits with a vague error message that doesn't identify which output caused the failure:
Benefits of this PR:
Screenshot shows the intended behavior: collector continues running and errors are properly surfaced at the exporter level.
Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
No disruptive user impact expected.
How to test this PR locally
build and install elastic-agent from this branch with the following configuration
Related issues
N/A
This is an automatic backport of pull request #10343 done by [Mergify](https://mergify.com).